Systems and methods for performing network configurable access and data transfer procedures

ABSTRACT

Mobile originated and terminated data transmissions are discussed. Communication devices such as user equipment (UE) can be dynamically configured by a network to send and receive data. When a UE connects to a new network, the network can determine mobility of the UE and/or the network resource allocation granularity. Based at least on the network&#39;s determinations, the UE can be configured such that access data having a comparatively long life span is used and reused for multiple data transmissions. In some scenarios, access data can be refreshed after expiration of a period of time. Refresh time can be equal to expected life span of reusable access data. After UE configuration, the UE performs mobile originated and terminated data transmissions according to the configuration. Other aspects, embodiments, and features are also claimed and described.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of co-pending, commonlyassigned, patent application Ser. No. 15/089,412 entitled “SYSTEMS ANDMETHODS FOR PERFORMING NETWORK CONFIGURABLE ACCESS AND DATA TRANSFERPROCEDURES,” filed Apr. 1, 2016, which claims the benefit of andpriority to U.S. Provisional Patent Application No. 62/261,080 entitled,“SYSTEMS AND METHODS FOR PERFORMING NETWORK CONFIGURABLE ACCESS AND DATATRANSFER PROCEDURES,” filed on Nov. 30, 2015, the disclosures of whichare hereby incorporated herein by reference as if fully set forth belowin its entirety and for all applicable purposes.

TECHNICAL FIELD

Aspects of the present disclosure relate generally to wirelesscommunication systems, and more particularly, to wireless networksoperable to configure access procedures and data transfer procedures.

INTRODUCTION

A wireless communication network may include a number of base stationsor node Bs that can support communication for a number of userequipments (UEs). A UE may communicate with a base station via downlink(DL) and uplink (UL). The downlink (or forward link) refers to thecommunication link from the base station to the UE, and the uplink (orreverse link) refers to the communication link from the UE to the basestation.

A base station may transmit data and control information on the downlinkto a UE and/or may receive data and control information on the uplinkfrom the UE. On the downlink, a transmission from the base station mayencounter interference due to transmissions from neighbor base stationsor from other wireless radio frequency (RF) transmitters. On the uplink,a transmission from the UE may encounter interference from uplinktransmissions of other UEs communicating with the neighbor base stationsor from other wireless RF transmitters. This interference may degradeperformance on both the downlink and uplink.

With the growing demand for mobile broadband access comes an increase incommunications between an eNB and a UE. Traditionally, a UE is notconstantly connected with an eNB because a constant connection wouldwaste network bandwidth and UE battery life. As such, every time adisconnected UE desires to send or receive data from the network, aseries of specific steps and communications between the eNB and the UEare performed in order to setup a two way connection between the UE andeNB before the desired data is transmitted. This process hastraditionally been called the Random Access Procedure (RAP).

RAP involves a great number of setup steps before a connection isestablished and data is transmitted. Traditionally, all of the mobileoriginated (MO) data transmission steps are performed before each MOtransmission, and every mobile terminated (MT) transmission step isperformed before every MT transmission. Typically, all of the setupsteps are repeated a multitude of times throughout an hour tying up aconsiderable about of network bandwidth and UE battery life. Further,because these steps are repeated for each transmission, the setup stepsincrease data latency.

BRIEF SUMMARY OF SOME EXAMPLES

The following summarizes some aspects of the present disclosure toprovide a basic understanding of the discussed technology. This summaryis not an extensive overview of all contemplated features of thedisclosure, and is intended neither to identify key or critical elementsof all aspects of the disclosure nor to delineate the scope of any orall aspects of the disclosure. Its sole purpose is to present someconcepts of one or more aspects of the disclosure in summary form as aprelude to the more detailed description that is presented later.

In one aspect of the disclosure, a method for transmitting datacomprises receiving UE access data and saving at least a portion of theUE access data. Subsequent to the saving, determining that data is to betransferred and utilizing at least a portion of the previously saved UEaccess data to send more than one data transmission, wherein the morethan one data transmissions are sent at different times.

In an additional aspect of the disclosure, a method for receiving datacomprises determining that the network desires to send data, receivingthe data, and utilizing previously saved UE access data to decode thereceived data. The method may further comprise refreshing the previouslysaved access data based on a determination that a predetermined timeperiod has expired.

In an additional aspect of the disclosure, a method of configuring a UEcomprises determining whether the UE is mobile, determining a resourceallocation granularity of a network serving the UE, and configuring theUE's method of transmitting data based at least on the mobilitydetermination and the resource allocation granularity determination. Inembodiments wherein the mobility determination determines that the UE isa non-mobile UE, the method may further comprise setting a predeterminedperiod of time to be less than or equal to an expected life span of UEaccess data, and configuring the UE to transmit data according to thefollowing steps: receiving the UE access data, saving at least a portionof the UE access data, subsequent to the saving, determining that datais to be transferred, and utilizing at least a portion of the previouslysaved UE access data to transmit more than one data transmission.

In an additional aspect of the disclosure, a system for transmittingdata comprises means for receiving UE access data, means for saving atleast a portion of the UE access data, subsequent to the saving, meansfor determining that data is to be transferred, and means for utilizingat least a portion of the previously saved UE access data to send morethan one data transmission, wherein the more than one data transmissionsare sent at different times.

In an additional aspect of the disclosure, a system for receiving datacomprises means for determining that the network desires to send data,means for receiving the data, means for utilizing previously saved UEaccess data to decode the received data, and means for refreshing thepreviously saved access data based on a determination that apredetermined time period has expired.

In an additional aspect of the disclosure, a system for configuring aUE's transmission procedure comprises means for determining whether theUE is mobile, means for determining a resource allocation granularity ofa network serving the UE, and means for configuring the UE'stransmission procedure based at least on the mobility determination andthe resource allocation granularity determination. In embodimentswherein the mobility determination determines that the UE is anon-mobile UE, the system may further comprise means for setting apredetermined period of time to be less than or equal to an expectedlife span of UE access data, and configuring the UE to transmit dataaccording to the following steps: receiving the UE access data, savingat least a portion of the UE access data, subsequent to the saving,determining that data is to be transferred, and utilizing at least aportion of the previously saved UE access data to transmit more than onedata transmission.

In an additional aspect of the disclosure, a system for transmittingdata comprises a UE comprising a controller processor, one or moreantenna, a transmit processor, and a memory, is operable to receive UEaccess data and save at least a portion of the UE access data.Subsequent to the saving, the UE is further operable to determine thatdata is to be transferred and utilizes at least a portion of thepreviously saved UE access data to send more than one data transmission,wherein the more than one data transmissions are sent at differenttimes.

In an additional aspect of the disclosure, a system for receiving datacomprises a UE operable to determine that a network desires to send dataand further operable to receive the data, wherein the UE utilizespreviously saved UE access data to decode the received data. Further,the UE refreshes the previously saved access data based on adetermination that a predetermined time period has expired.

In an additional aspect of the disclosure, a system for configuring aUE's transmission procedures comprises a network computer operable todetermine whether the UE is mobile and determine a resource allocationgranularity of a network serving the UE, wherein the UE's transmissionprocedures are configured based at least on the mobility determinationand the resource allocation granularity determination. In embodimentswherein the mobility determination determines that the UE is anon-mobile UE, the network computer is further configured to set apredetermined period of time to be less than or equal to an expectedlife span of UE access data, and configure the UE to transmit dataaccording to the following steps: receiving the UE access data, savingat least a portion of the UE access data, subsequent to the saving,determining that data is to be transferred, and utilizing at least aportion of the previously saved UE access data to transmit more than onedata transmission.

In an additional aspect of the disclosure, a non-transitorycomputer-readable medium having program code recorded thereon, whereinthe program code comprises program code for causing a UE to receive UEaccess data, program code for causing the UE to save at least a portionof the UE access data, program code for causing the UE to determine,subsequent to the saving, that data is to be transferred, and programcode for causing the UE to utilize at least a portion of the previouslysaved UE access data to send more than one data transmission, whereinthe more than one data transmissions are sent at different times.

In an additional aspect of the disclosure, a non-transitorycomputer-readable medium having program code recorded thereon, whereinthe program code comprises program code for causing a UE to determinethat the network desires to send data, program code for causing a UE toreceive the data, and program code for causing a UE to utilizepreviously saved UE access data to decode the received data, wherein thepreviously saved access data is refreshed when a predetermined timeperiod has expired.

In an additional aspect of the disclosure, a non-transitorycomputer-readable medium having program code recorded thereon, whereinthe program code comprises program code for causing a network computerto determine whether a UE is mobile, program code for causing a networkcomputer to determine a resource allocation granularity of a networkserving the UE, and program code for causing a network computer toconfigure the UE's transmission procedure based at least on the mobilitydetermination and the resource allocation granularity determination.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

Other aspects, features, and embodiments of the present invention willbecome apparent to those of ordinary skill in the art, upon reviewingthe following description of specific, exemplary embodiments of thepresent invention in conjunction with the accompanying figures. Whilefeatures of the present invention may be discussed relative to certainembodiments and figures below, all embodiments of the present inventioncan include one or more of the advantageous features discussed herein.In other words, while one or more embodiments may be discussed as havingcertain advantageous features, one or more of such features may also beused in accordance with the various embodiments of the inventiondiscussed herein. In similar fashion, while exemplary embodiments may bediscussed below as device, system, or method embodiments it should beunderstood that such exemplary embodiments can be implemented in variousdevices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentdisclosure may be realized by reference to the following drawings. Inthe appended figures, similar components or features may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 is a block diagram illustrating details of a wirelesscommunication system according to some embodiments.

FIG. 2 is a block diagram conceptually illustrating a design of a basestation/eNB and a UE configured according to some embodiments.

FIG. 3 is a flow diagram illustrating an example method of an EventDriven Access and Data Transmission Procedure according to someembodiments.

FIG. 4 is a flow diagram illustrating an example method of a NetworkConfigurable Access and Data Transmission Procedure according to someembodiments.

FIG. 5 is a flow diagram illustrating another example of a NetworkConfigurable Access and Data Transmission Procedure according to someembodiments.

FIG. 6 is a flow diagram illustrating a method which configures theAccess and Data Transmission Procedures for a UE according to someembodiments.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings and appendix, is intended as a description of variousconfigurations and is not intended to limit the scope of the disclosure.Rather, the detailed description includes specific details for thepurpose of providing a thorough understanding of the inventive subjectmatter. It will be apparent to those skilled in the art that thesespecific details are not required in every case and that, in someinstances, well-known structures and components are shown in blockdiagram form for clarity of presentation.

This disclosure relates generally to providing or participating inauthorized shared access between two or more wireless communicationssystems, also referred to as wireless communications networks. Invarious embodiments, the techniques and apparatus may be used forwireless communication networks such as code division multiple access(CDMA) networks, time division multiple access (TDMA) networks,frequency division multiple access (FDMA) networks, orthogonal FDMA(OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks,GSM networks, as well as other communications networks. As describedherein, the terms “networks” and “systems” may be used interchangeably.

A CDMA network may implement a radio technology such as universalterrestrial radio access (UTRA), cdma2000, and the like. UTRA includeswideband-CDMA (W-CDMA) and low chip rate (LCR). CDMA2000 covers IS-2000,IS-95, and IS-856 standards.

A TDMA network may implement a radio technology such as Global Systemfor Mobile Communications (GSM). 3GPP defines standards for the GSM EDGE(enhanced data rates for GSM evolution) radio access network (RAN), alsodenoted as GERAN. GERAN is the radio component of GSM/EDGE, togetherwith the network that joins the base stations (for example, the Ater andAbis interfaces) and the base station controllers (interfaces, etc.).The radio access network represents a component of a GSM network,through which phone calls and packet data are routed from and to thepublic switched telephone network (PSTN) and Internet to and fromsubscriber handsets, also known as user terminals or user equipments(UEs). A mobile phone operator's network may comprise one or moreGERANs, which may be coupled with UTRANs in the case of a UMTS/GSMnetwork. An operator network may also include one or more LTE networks,and/or one or more other networks. The various different network typesmay use different radio access technologies (RATS) and radio accessnetworks (RANs).

An OFDMA network may implement a radio technology such as evolved UTRA(E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and thelike. UTRA, E-UTRA, and GSM are part of universal mobiletelecommunication system (UMTS). In particular, long term evolution(LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS andLTE are described in documents provided from an organization named “3rdGeneration Partnership Project” (3GPP), and cdma2000 is described indocuments from an organization named “3rd Generation Partnership Project2” (3GPP2). These various radio technologies and standards are known orare being developed. For example, the 3rd Generation Partnership Project(3GPP) is a collaboration between groups of telecommunicationsassociations that aims to define a globally applicable third generation(3G) mobile phone specification. 3GPP long term evolution (LTE) is a3GPP project aimed at improving the universal mobile telecommunicationssystem (UMTS) mobile phone standard. The 3GPP may define specificationsfor the next generation of mobile networks, mobile systems, and mobiledevices. For clarity, certain aspects of the apparatus and techniquesmay be described below for LTE implementations or in an LTE-centric way,and LTE terminology may be used as illustrative examples in portions ofthe description below; however, the description is not intended to belimited to LTE applications. Indeed, the present disclosure is concernedwith shared access to wireless spectrum between networks using differentradio access technologies or radio air interfaces.

A new carrier type based on LTE/LTE-A including in unlicensed spectrumhas also been suggested that can be compatible with carrier-grade WiFi,making LTE/LTE-A with unlicensed spectrum an alternative to WiFi.LTE/LTE-A, when operating in unlicensed spectrum, may leverage LTEconcepts and may introduce some modifications to physical layer (PHY)and media access control (MAC) aspects of the network or network devicesto provide efficient operation in the unlicensed spectrum and meetregulatory requirements. The unlicensed spectrum used may range from aslow as several hundred Megahertz (MHz) to as high as tens of Gigahertz(GHz), for example. In operation, such LTE/LTE-A networks may operatewith any combination of licensed or unlicensed spectrum depending onloading and availability. Accordingly, it may be apparent to one ofskill in the art that the systems, apparatus and methods describedherein may be applied to other communications systems and applications.

System designs may support various time-frequency reference signals forthe downlink and uplink to facilitate beamforming and other functions. Areference signal is a signal generated based on known data and may alsobe referred to as a pilot, preamble, training signal, sounding signal,and the like. A reference signal may be used by a receiver for variouspurposes such as channel estimation, coherent demodulation, channelquality measurement, signal strength measurement, and the like. MIMOsystems using multiple antennas generally provide for coordination ofsending of reference signals between antennas; however, LTE systems donot in general provide for coordination of sending of reference signalsfrom multiple base stations or eNBs.

In some implementations, a system may utilize time division duplexing(TDD). For TDD, the downlink and uplink share the same frequencyspectrum or channel, and downlink and uplink transmissions are sent onthe same frequency spectrum. The downlink channel response may thus becorrelated with the uplink channel response. Reciprocity may allow adownlink channel to be estimated based on transmissions sent via theuplink. These uplink transmissions may be reference signals or uplinkcontrol channels (which may be used as reference symbols afterdemodulation). The uplink transmissions may allow for estimation of aspace-selective channel via multiple antennas.

In LTE implementations, orthogonal frequency division multiplexing(OFDM) is used for the downlink—that is, from a base station, accesspoint or eNodeB (eNB) to a user terminal or UE. Use of OFDM meets theLTE requirement for spectrum flexibility and enables cost-efficientsolutions for very wide carriers with high peak rates, and is awell-established technology. For example, OFDM is used in standards suchas IEEE 802.11a/g, 802.16, High Performance Radio LAN-2 (HIPERLAN-2wherein LAN stands for Local Area Network) standardized by the EuropeanTelecommunications Standards institute (ETSI), Digital VideoBroadcasting (DVB) published by the Joint Technical Committee of ETSI,and other standards.

Time frequency physical resource blocks (also denoted here in asresource blocks or “RBs” for brevity) may be defined in OFDM systems asgroups of transport carriers (e.g. sub-carriers) or intervals that areassigned to transport data. The RBs are defined over a time andfrequency period. Resource blocks are comprised of time-frequencyresource elements (also denoted here in as resource elements or “REs”for brevity), which may be defined by indices of time and frequency in aslot. Additional details of LTE RBs and REs are described in the 3GPPspecifications, such as, for example, 3GPP TS 36.211.

UMTS LTE supports scalable carrier bandwidths from 20 MHz down to 1.4MHZ. In LIE, an RB is defined as 12 sub-carriers when the subcarrierbandwidth is 15 kHz or 24 sub-carriers when the sub-carrier bandwidth is7.5 kHz. In an exemplary implementation, in the time domain there is adefined radio frame that is 10 ms long and consists of 10 subframes of 1millisecond (ms) each. Every subframe consists of 2 slots, where eachslot is 0.5 ms. The subcarrier spacing in the frequency domain in thiscase is 15 kHz. Twelve of these subcarriers together (per slot)constitute an RB, so in this implementation one resource block is 180kHz. Six Resource blocks fit in a carrier of 1.4 MHz and 100 resourceblocks fit in a carrier of 20 MHz.

Various other aspects and features of the disclosure are furtherdescribed below. It should be apparent that the teachings herein may beembodied in a wide variety of forms and that any specific structure,function, or both being disclosed herein is merely representative andnot limiting. Based on the teachings herein one of an ordinary level ofskill in the art should appreciate that an aspect disclosed herein maybe implemented independently of any other aspects and that two or moreof these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. For example,a method may be implemented as part of a system, device, apparatus,and/or as instructions stored on a computer readable medium forexecution on a processor or computer. Furthermore, an aspect maycomprise at least one element of a claim.

FIG. 1 shows a wireless network 100 for communication, which may be anLTE-A network (other types of networks may also be utilized). Thewireless network 100 includes a number of evolved node Bs (eNBs) 105 andother network entities. An eNB may be a station that communicates withthe LTEs and may also be referred to as a base station, a node B, anaccess point, and the like. Each eNB 105 may provide communicationcoverage for a particular geographic area. The term “cell” can refer tothis particular geographic coverage area of an eNB and/or an eNBsubsystem serving the coverage area, depending on the context in whichthe term is used.

eNB may provide communication coverage for a macro cell or a small cell,such as a pico cell or a femto cell, and/or other types of cell. A macrocell generally covers a relatively large geographic area (e.g., severalkilometers in radius) and may allow unrestricted access by UEs withservice subscriptions with the network provider. A small cell, such as apico cell, would generally cover a relatively smaller geographic areaand may allow unrestricted access by UEs with service subscriptions withthe network provider. A small cell, such as a femto cell, would alsogenerally cover a relatively small geographic area (e.g., a home) and,in addition to unrestricted access, may also provide restricted accessby UEs having an association with the femto cell (e.g., UEs in a closedsubscriber group (CSG), UEs for users in the home, and the like). An eNBfor a macro cell may be referred to as a macro eNB. An eNB for a smallcell may be referred to as a small cell eNB, a pico eNB, femto eNB or ahome eNB. In the example shown in FIG. 1, the eNBs 105 a, 105 b and 105c are macro eNBs for the macro cells 110 a, 110 b and 110 c,respectively. The eNBs 105 x, 105 y, and 105 z are small cell eNBs,which may include pico or femto eNBs that provide service to small cells110 x, 110 y, and 110 z, respectively. An eNB may support one ormultiple (e.g., two, three, four, and the like) cells.

The wireless network 100 may support synchronous or asynchronousoperation. For synchronous operation, the eNBs may have similar frametiming, and transmissions from different eNBs may be approximatelyaligned in time. Synchronous networks may organize cells into zones,wherein a zone comprises a plurality of cells. The zones of a wirelessnetwork may allocate zone specific resources such that a UE may movefreely throughout a zone using the same zone specific resources as ittravels from one cell to another. For asynchronous operation, the eNBsmay have different frame timing, and transmissions from different eNBsmay not be aligned in time.

The UEs 115 are dispersed throughout the wireless network 100, and eachUE may be stationary or mobile. A UE may also be referred to as aterminal, a mobile station, a subscriber unit, a station, or the like. AUE may be a cellular phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, atablet computer, a laptop computer, a cordless phone, a wireless localloop (WLL) station, watch, or the like. Regarding the Internet of Things(IoT), a UE may be referred to as a IoT UE which may be an appliance,thermostat, water meter, electric meter, gas meter, sprinkler system,refrigerator, hot water heater, oven, car, navigation system, pacemaker, implanted medical device, location tracker, bicycle computer,entertainment device, television, monitor, vehicular component, vendingmachine, medical device, and the like. A UE may be able to communicatewith macro eNBs, pico eNBs, femto eNBs, relays, and the like. In FIG. 1,a lightning bolt (e.g., communication links 125) indicates desiredtransmissions between a UE and a serving eNB, which is an eNB designatedto serve the UE on the downlink and/or uplink, or desired transmissionbetween eNBs.

LTE/-A utilizes orthogonal frequency division multiplexing (OFDM) on thedownlink and single-carrier frequency division multiplexing (SC-FDM) onthe uplink. OFDM and SC-FDM partition the system bandwidth into multiple(K) orthogonal subcarriers, which are also commonly referred to astones, bins, or the like. Each subcarrier may be modulated with data. Ingeneral, modulation symbols are sent in the frequency domain with OFDMand in the time domain with SC-FDM. The spacing between adjacentsubcarriers may be fixed, and the total number of subcarriers (K) may bedependent on the system bandwidth. For example, K may be equal to 72,180, 300, 600, 900, and 1200 for a corresponding system bandwidth of1.4, 3, 5, 10, 15, or 20 megahertz (MHz), respectively. The systembandwidth may also be partitioned into sub-bands. For example, asub-band may cover 1.08 MHz, and there may be 1, 2, 4, 8 or 16 sub-bandsfor a corresponding system bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz,respectively. The devices illustrated in FIG. 1 are operable to carryout the techniques and operations disclosed herein.

As explained above, the growing demand for mobile broadband access hascreated an increase in communications between an eNB and a UE.Traditionally, all of the mobile originated (MO) data transmission stepsare performed before each MO transmission, and every mobile terminated(MT) transmission step is performed before every MT transmission.Typically, all of the setup steps are repeated a multitude of timesthroughout an hour tying up a considerable about of network bandwidthand UE battery life. Further, because these steps are repeated for eachtransmission, the setup steps increase data latency. As such, it wouldbe desirable to have systems and methods that allow for the reduction ofthe aforementioned steps and communications prior to MO and/or MTcommunications. That being said, there may be times when performing mostor all of the aforementioned steps may be appropriate due to the type ofdata being sent, the mobility of the UE, and/or the status of the UE.Thus, it would be farther desirable to have systems and methods operableto determine which steps and communications are appropriate given thecircumstances and configure the LTE to perform a reduced set of stepsand communications when appropriate and perform a robust set of stepsand communications when appropriate.

FIG. 2 shows a block diagram of a design of a base station/eNB 105 and aUE 115, which may be one of the base stations/eNBs and one of the UEs inFIG. 1. For a restricted association scenario, the eNB 105 may be thesmall cell eNB 105 z in FIG. 1, and the UE 115 may be the UE 115 z,which in order to access small cell eNB 105 z, would be included in alist of accessible UEs for small cell eNB 105 z. The eNB 105 may also bea base station of some other type. The eNB 105 may be equipped withantennas 234 a through 234 t, and the UE 115 may be equipped withantennas 252 a through 252 r.

At the eNB 105, a transmit processor 220 may receive data from a datasource 212 and control information from a controller/processor 240. Thecontrol information may be for the PBCH, PCFICH, PHICH, PDCCH, etc. Thedata may be for the PDSCH, etc. The transmit processor 220 may process(e.g., encode and symbol map) the data and control information to obtaindata symbols and control symbols, respectively. The transmit processor220 may also generate reference symbols, e.g., for the PSS, SSS, andcell-specific reference signal. A transmit (TX) multiple-inputmultiple-output (MIMO) processor 230 may perform spatial processing(e.g., precoding) on the data symbols, the control symbols, and/or thereference symbols, if applicable, and may provide output symbol streamsto the modulators (MODs) 232 a through 232 t. Each modulator 232 mayprocess a respective output symbol stream (e.g., for OFDM, etc.) toobtain an output sample stream. Each modulator 232 may further process(e.g., convert to analog, amplify, filter, and upconvert) the outputsample stream to obtain a downlink signal. Downlink signals frommodulators 232 a through 232 t may be transmitted via the antennas 234 athrough 234 t, respectively.

At the UE 115, the antennas 252 a through 252 r may receive the downlinksignals from the eNB 105 and may provide received signals to thedemodulators (DEMODs) 254 a through 254 r, respectively. Eachdemodulator 254 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator 254 may further process the input samples (e.g., for OFDM,etc.) to obtain received symbols. A MIMO detector 256 may obtainreceived symbols from all the demodulators 254 a through 254 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 258 may process (e.g., demodulate,deinterleave, and decode) the detected symbols, provide decoded data forthe UE 115 to a data sink 260, and provide decoded control informationto a controller/processor 280.

On the uplink, at the UE 115, a transmit processor 264 may receive andprocess data (e.g., for the PUSCH) from a data source 262 and controlinformation (e.g., for the PUCCH) from the controller/processor 280. Thetransmit processor 264 may also generate reference symbols for areference signal. The symbols from the transmit processor 264 may beprecoded by a TX MIMO processor 266 if applicable, further processed bythe modulators 254 a through 254 r (e.g., for SC-FDM, etc.), andtransmitted to the eNB 105. At the eNB 105, the uplink signals from theUE 115 may be received by the antennas 234, processed by thedemodulators 232, detected by a MIMO detector 236 if applicable, andfurther processed by a receive processor 238 to obtain decoded data andcontrol information sent by the UE 115. The processor 238 may providethe decoded data to a data sink 239 and the decoded control informationto the controller/processor 240.

The controllers/processors 240 and 280 may direct the operation at theeNB 105 and the UE 115, respectively. The controller/processor 240and/or other processors and modules at the eNB 105 may perform or directthe execution of various processes for the techniques described herein.The controllers/processor 280 and/or other processors and modules at theUE 115 may also perform or direct the execution of the functional blocksillustrated in FIGS. 3-6, and/or other processes for the techniquesdescribed herein. The memories 242 and 282 may store data and programcodes for the eNB 105 and the UE 115, respectively. A scheduler 244 mayschedule UEs for data transmission on the downlink and/or uplink.

FIG. 3 shows an example flow diagram of method 300, which is an EventDriven Access and Data Transmission Procedure 300. In method 300, anevent triggers performance of all the steps of the Event Driven Accessand Data Transmission Procedure 300. An example triggering event is ascheduled reading report, wherein the UE is schedule to take a reading(e.g., temperature reading) and report the reading to the network. Upontaking the reading, the UE would perform method 300 in order to transmitthe mobile originated (MO) data to the network. Another exampletriggering event is the reception of a Keep Alive (KA) message or apaging message from the eNB warning the UE that a data transmission willsoon be sent to the UE. A KA is used to tell the UE to wake up and setupa connection with the eNB, for example, because the eNB is getting readyto send mobile terminated (MT) data to the UE. In embodiments, a KA maybe as small as one bit.

In 301, an eNB broadcasts synchronization information, which may includebut is not limited to, Primary Synchronization Signals (PSS), SecondarySynchronization Signals (SSS), downlink reference signals, MasterInformation Block (MIB), Physical Hybrid-ARQ Indicator Channel (PHICH)configuration, System Frame Number, QPSK modulation, cell-specificscrambling, basic network data, and the like. In 302, one or more UEreceives the eNB broadcasted synchronization information. The eNBbroadcasted synchronization information may be received directly fromthe eNB or from another device.

Upon a triggering event occurring, it is determined that communicationbetween the UE and eNB is desired. If the triggered communication is tobe MO, the method performs alternative A. Alternative A begins with 303a, wherein the UE sends a Chirp using at least a portion of thesynchronization information, which may include the Random Access ChannelReference Signal (RACH-RS), the UE ID, Buffer Status Report, and/or thelike. In embodiments, the eNB may not have network resources availableat the time the Chirp is received. For example, the eNB may not have anUL channel available at the time the UE sends the Chirp. In such acircumstance, the eNB has the option to respond to the Chirp by sendinga KA message to the UE indicting that the eNB is willing to receive thedata but does not currently have the resources available (optional 303b). Upon network resources becoming available, the eNB may proceed to304.

Alternatively, if the triggered communication is to be MT, the methodperforms alternative B. In alterative B, the UE has the option ofsending a Chirp using at least a portion of the synchronizationinformation, which may include the Random Access Channel ReferenceSignal (RACH-RS), the UE ID, Buffer Status Report, and/or the like. In303 d, the eNB sends a Keep Alive (KA) to the UE. After steps 303 b or303 d (depending on which of the alternative routes were taken), themethod moves to 304.

At 304, in response to the Chirp or KA, the eNB creates and sends aConnection Setup, which may include network information, such as but notlimited to, a Cell ID, the UL or DL assignment, a Timing Advance (TA), aModulation and Coding Scheme (MCS), Channel State Information (CSI),and/or the like. The UE may receive the Connection Setup directly fromthe eNB or from another device.

In 305 the data payload is send on the assigned UL or DL. In a MOexample, the UE sends the data payload (e.g., a temperature reading) theeNB on the UL in 305. If a MT example, the eNB sends the data payload tothe UE on the DL in 305.

After the initial data payload is transmitted in 305, the UE and eNB maymaintain the connection so that additional data payloads may becommunicated back and forth between the UE and eNB. Upon the UE and eNBceasing to send data to each other for a period of time, 306 maytransition the UE into an Idle state or Standby mode. In 307, anothertriggering event occurs, thereby causing all steps of the Event DrivenAccess and Transmission Data Procedure 300 to repeat again.

The Event Driven Access and Data Transmission Procedure of FIG. 3 can berepeated each and every time an event occurs, for example, when a datatransfer is initiated. As such, while method 300 performs less steps ascompared to traditional RAP, steps of this method may be repeatedseveral times throughout a time period (e.g., minute, hours, day, andthe like). Performing the steps of method 300 may consume a considerableamount of resources including time, battery life, and network traffic.When appropriate, it would be desirable to conserve the aforementionedresources by offering a method that allows one or more of the steps ofFIG. 3 to be skipped for defined periods of time.

FIG. 4 is an example Network Configurable Access and Data TransmissionProcedure useful for mobile originated (MO) data transfers. It isgenerally designed to reduce the Access Procedure's frequency so some ofmethod 300's actions may be skipped. Method 400 is split into twoprocedures: the Access Procedure 400 a, which is performed once during apredetermined time period (e.g., once an hour, once a day, once a week,or the like) and the Data Transmission Procedure 400 b, which isperformed at the initiation of each data transfer. Thus, AccessProcedure 400 a is performed less frequently as compared to DataTransmission Procedure 400 b. Further, according to Data TransmissionProcedure 400 b, multiple data transmissions are conducted using andreusing access data saved during Access Procedure 400 a until thepredetermined time period expires. When the predetermined time periodexpires, the Access Procedure 400 a is performed again to allow savedaccess data to be refreshed. As such, method 400 minimizes and/oreliminates the repeated expenditure of time, battery life, and datatraffic involved in performing the steps of the Access Procedure 400 aby minimizing its frequency. Further, the network determines whether theUE should be configured to operate according to the Event Driven Accessand Data Transmission Procedure 300 or the Network Configurable Accessand Data Transmission Procedure 400.

In 401, an eNB broadcasts synchronization information. Synch informationmay include but is not limited to, Primary Synchronization Signals(PSS), Secondary Synchronization Signals (SSS), downlink referencesignals, Master Information Block (MIB), Physical Hybrid-ARQ IndicatorChannel (PHICH) configuration, System Frame Number, QPSK modulation,cell-specific scrambling, basic network data, and the like. In 402, oneor more UE receives the eNB broadcasted synchronization information. TheeNB broadcasted synchronization information may be received directlyfrom the eNB or from another device.

At 403, the UE initiates the Access Procedure 400 a by sending a Chirp,which may include the UE ID, Buffer Status Report, Random Access ChannelReference Signal (RACH-RS), and/or the like. The eNB receives the Chirpeither directly from the UE or from another device. In a NetworkConfigurable Access and Data Transmission Procedure 400, the networkconfigures when and if Access Procedure 400 a is performed. For example,the network may configure the UE to initiate the Access Procedure 400 aupon the UE powering up, upon the UE entering a new cell, upon the UEentering a new zone, upon the UE entering a new network, and/or upon theexpiration of a predetermined period of time, x, which is set by thenetwork. Methodology the network uses to set the predetermined timeperiod will be discussed below with reference to FIG. 6.

In embodiments, the eNB may not have network resources available at thetime the Chirp is received. For example, the eNB may not have an ULchannel available at the time the UE sends the Chirp. In such acircumstance, the eNB has the option respond to the Chirp by sending aKA message to the UE indicting that the eNB is willing to receive thedata but does not currently have the resources available (optional 403a). Upon network resources becoming available, the eNB may proceed to404 wherein the eNB creates and sends the Connection Setup.

At 404, in response to receiving the Chirp, the eNB creates and sends aConnection Setup, which may include network information, such as but notlimited to, a Cell ID, a Timing Advance (TA), a Modulation and CodingScheme (MCS), Channel State Information (CSI), a UL assignment, and/orthe like. SIB information may also be sent to the UE. In embodiments,the SIB information may be sent in a separate transmission subsequent tothe transmission that included the Cell ID, TA, MCS, CSI, etc. The UEmay receive the Connection Setup directly from the eNB or from anotherdevice.

In 405, the UE saves access data for future transmissions. Preferably,the saved access data is system, information that is unlikely to changefor the predetermined period of time (e.g. an hour, a day, days, weeks,years, and the like) such as the Cell ID, the TA, the MCS, a resourceconfiguration within the SIB, and/or the like. An uplink and downlinkassignment is likely to change during the predetermined period of time,so the uplink and downlink assignment may be omitted from the savedaccess data. In some embodiments, such as UEs operating in a networkthat allocates zone specific resources and/or UEs sending small data,405 may choose to exclude the TA from the saved access data. In thesecircumstances, the TA may be omitted from the saved access data becausethe TA may not be needed to transfer data at a later time. Steps 403-405may be referred to as the UE's Access Procedure 400 a, and theinformation saved during the Access Procedure 400 a may be used by theUE at a later time to transmit data to the eNB.

As explained above, the network configures when and if the AccessProcedure 400 a is performed. If the network has configured the AccessProcedure 400 a to be performed upon expiration of a predeterminedperiod of time, x, then at 406, the predetermined period of time begins.As explained above, the saved access data is saved for future use, andis unlikely to change during the predetermined period of time. As such,the predetermined period of time, x, is set to match the expected lifespan of the saved access data. For example, if the access data isexpected to become stale after an hour, then x is set to one hour orless. If the access data is expected to become stale after a day, x isset to one day or less. The network is free to configure x to be anyvalue and preferably is set to match the expected life span of the savedaccess data.

406 monitors whether the predetermined period of time has expired. Atthe expiration of the predetermined period of time, the method moves to401 and the Access Procedure 400 a is repeated in order to refresh thesaved access data. Prior to the predetermined period of time expiring,the UE may perform any number of operations including but not limited totransitioning into an Idle state or Standby mode.

Among the aforementioned operations the UE may perform, one or more DataTransmission Procedure 400 b may be performed before the expiration ofthe predetermined period of time. At 407, the UE decides to send data tothe network, which initiates the Data Transmission Procedure 400 b.While the Data Transmission Procedure 400 b may be used to send severaldifferent types of data, small data is particularly suitable fortransmission via Data Transmission Procedure 400 b. Small data is a datapacket that is comparatively smaller in size than a typical data packet.For example, small data may be limited to 1-300 bits while a typicaldata packet may range in size from 300-1000 s of bits. Because the smalldata has comparatively less bits than traditional data, small data mayinclude a comparatively smaller payload and a comparatively smalleroverhead. For example, small data may be limited to the small datapayload and UE ID. Because small data is comparatively smaller thantypical data packets, collisions and data loss are of less concern.Thus, small data may safely be treated differently from typical datapackets. Further, small data may involve a data packet that the UEdesires to send but to which no connection setup is desired. Forexample, small data may be time sensitive readings of the UE that arescheduled to be reported to the eNB, but to which no eNB response, otherthan an ACK/NACK response, is desired. In a more specific example, theUE may be configured to send a water meter reading every hour, but otherthan an ACK/NACK, desires no response from the network regarding thewater meter reading. Because the UE desires no response, a two wayconnection between the UE and eNB is not necessary at the time the smalldata is sent. As such, it is desirable for the UE to send small data tothe eNB without expending time or battery life establishing a two wayconnection, for example the two way connection required for a voice callor to browse the Internet.

The Data Transmission Procedure 400 b, e.g., steps 407-410, sends data(e.g., small data) more quickly and efficiently as compared atraditional uplink of data sent in a two way communication between theUE and eNB. In embodiments, the Data Transmission Procedure 400 b may beperformed substantially more often than the Access Procedure 400 a. Forexample, the UE may be configured to take interval readings (e.g., in 15minute intervals, 30 minute intervals, hourly, and the like) and/or takereadings in response to an event (e.g., when a door opens, when a lightis turned on or off, when a TV or radio channel is changed) and reportthe readings using the Data Transmission Procedure 400 b while incomparison, the Access Procedure 400 a is only performed afterexpiration of an extended period of time (e.g., a day, days, a week,weeks, and the like).

In 407, the UE decides to send a data transmission. The method thenmoves to 408, which is similar to 402. In 408, the UE receives thesynchronization information that the eNB is broadcasting at that time.The synchronization information may include but is not limited to,Primary Synchronization Signals (PSS), Secondary Synchronization Signals(SSS), downlink reference signals, Master Information Block (MIB),Physical Hybrid-ARQ Indicator Channel (PHICH) configuration, SystemFrame Number, QPSK modulation, cell-specific scrambling, basic networkdata, frame boundary, and/or the like.

In 409, the data is transmitted. The UE uses the current synchronizationinformation and at least a portion of the saved access information tosend an I-Chirp comprising the data payload to the eNB. Preferably, theI-Chirp is small data including the data payload and UE-ID. If the UEdecides to send another transmission before the predetermined timeperiod expires, steps 407-409 are repeated without repeating AccessProcedure 400 a. Further, once 406 determines the predetermined periodof time has expired, the method returns to 403 and the Access Procedure400 a is repeated in order to refresh the saved access data.

Optionally, the eNB may generate and send an ACK/NACK message inresponse to the I-Chirp. If this option is exercised, then uponreceiving a NACK, the UE may repeat 409, until an ACK is received, untila NACK time period has expired, and/or until a threshold number ofattempts have been made.

As explained, Data Transmission Procedure 400 b may be repeated severaltimes using some or all of the access data previously saved during 405.Traditionally, a Random Access Procedure and two way connection setup isperformed every time a data transmission is desired. Thus, thetraditional procedure consumes substantial time, battery life, and datatraffic performing multiple Random Access Procedures throughout the day.Method 400 performs its Access Procedure 400 a once during apredetermined time period (e.g., once an hour, once a day, once a week,or the like) and reuses the access data saved from the previouslyperformed Access Procedure 400 a for each Data Transmission Procedure400 b performed during that predetermined time period. Thus, method 400minimizes and/or prevents the repeated consumption of time, batterylife, and data traffic during that time period.

FIG. 5 is an example Network Configurable Access and Data TransmissionProcedure useful for mobile terminated (MT) data transfers, which isdesigned to reduce the Access Procedure's 500 a frequency therebyallowing several of the steps to be omitted when appropriate. Method 500is split into two procedures: the Access Procedure 500 a, which isperformed once during a predetermined time period (e.g., once a minute,once an hour, once a day, once a week, or the like) and the DataTransmission Procedure 500 b, wherein multiple data transmissions areconducted using and reusing access data saved during Access Procedure500 a until the predetermined time period expires. When thepredetermined time period expires, the Access Procedure 500 a isperformed again to refresh the saved access data. As such, method 500minimizes and/or eliminates the repeated expenditure of time, batterylife, and data traffic involved in the steps of the Access Procedure 500a by minimizing its frequency. Further, the network determines whetherthe UE should be configured to operate according to the Event DrivenAccess and Data Transmission Procedure 300 or the Network ConfigurableAccess and Data Transmission Procedure 500.

In method 500, the Access Procedure 500 a performs the same steps asthose disclosed in Access Procedure 400 a. Further, in 501, the method500 monitors whether the predetermined period of time has expired. Atthe expiration of the predetermined period of time, the method repeatsAccess Procedure 500 a. Prior to the predetermined period of timeexpiring, the UE may perform any number of operations including by notlimited to transitioning into an Idle state or Standby mode.

Among the aforementioned operations the UE may perform before theexpiration of the predetermined period of time is Data TransmissionProcedure 500 b. At 502, the eNB decides to send data to the UE, whichinitiates Data Transmission Procedure 500 b.

In 503, the eNB sends a Keep Alive (KA) message to the UE alerting theUE that a downlink (DL) transmission will soon be sent. The eNB may waitfor Chirp or KA occasion before sending the KA message in 503. In 504,the UE listens for the DL transmission. Upon receiving the DLtransmission, the UE decodes the DL transmission at least using some orall of the access data saved during the Access Procedure 500 a such asthe cell ID.

Data Transmission Procedure 500 b may be repeated several times prior toexpiration of the predetermined time period using at least some or allof the access data saved during Access Procedure 500 a. Traditionally, aRandom Access Procedure and two way connection setup is performed everytime the eNB decides to send a data transmission. Thus, the traditionalprocedure consumes substantial time, battery life, and data trafficperforming multiple Random Access Procedures throughout the day. Method500 performs its Access Procedure 500 a once during a predetermined timeperiod (e.g., once a minute, once an hour, once a day, once a week, orthe like) and reuses the access data saved from the previously performedAccess Procedure 500 a for each Data Transmission Procedure 500 bperformed during that predetermined time period. Thus, method 500minimizes and/or prevents the repeated consumption of time, batterylife, and data traffic during that time period.

FIGS. 3-5 illustrate various methods for data transmission. As mentionedabove, the network determines whether at any particular time one or moreparticular UEs should be configured to operate according to the EventDriven Access and Data Transmission Procedure 300 or the NetworkConfigurable Access and Data Transmission Procedures 400 and 500. FIG. 6shows an example flow diagram of method 600, wherein the networkdetermines which configuration is appropriate for a particular UE at aparticular time and then configures the manner in which the UE will sendMobile Originated (MO) data transmissions and receive Mobile Terminated(MT) data transmissions based on that determination.

In 601, a UE comes into communication with a new wireless communicationnetwork. In examples, the UE may be powered on or otherwise move into anarea covered by a different communication network. In 602, the methoddetermines whether the UE is a mobile UE or a non-mobile UE. If the UEis determined to be a non-mobile UE, the method moves to 603, whereinthe UE is configured to perform data transmissions according to themethods disclosed in FIGS. 4 and 5. Further, 603 sets the predetermineperiod of time, x. Because the UE is a non-mobile device, the savedaccess data of Access Procedures 400 a and 500 a is expected to have along life span. Thus, x is set to be a high value thereby minimizing thenumber of times the Access Procedure 400 a or 500 a is performed. Forexample, x may be set as high as 24 hours, 48 hours, once a week, or thelike. In 603, the network has the option of configuring the UE to ignoreTiming Advances (TA) and/or MCS when sending data transmissions. Ifdesired, the network may configure the UE to ignore TA and/or MCScontingent on the type of data being transferred (e.g., TA may beignored when transmitting small data). The UE remains in thisconfiguration until the UE leaves the serving network (604) and connectsto a new network (601).

If 602 determines that the UE is a mobile UE, the method moves to 605,wherein the system determines the allocation granularity of the networkresources. For example, some networks allocate cell specific resourcesand other networks allocate zone specific resources. In a network thatallocates cell specific resources, assigned resources of a first cellare not used when communicating with a second cell. For example, eachcell would send a UE a different SIB. In contrast, in a network thatallocates zone specific resources, a plurality of cells share resourceallocations. As such, zone specific resources are shared by a pluralityof cells such that zone allocated resources can be used by a UE tocommunicate with any or a plurality of the cells within the zone. Forexample, the UE could communicate with a first cell and a second cellusing the same SIB information.

If 605 determines that the network allocates cell specific resources,the method moves to 606, wherein the UE is configured to perform datatransmissions according to the method disclosed in FIG. 3. The UEremains in this configuration until the UE leaves the serving network(604) and connects to a new network (601).

If 605 determines that the network allocates zone specific resources,the method moves to 607, wherein the UE is configured to perform datatransmissions according to the methods disclosed in FIGS. 4 and 5.Further, 607 sets the predetermine period of time, x. Because the UE isa mobile device, the saved access data of Access Procedures 400 a and500 a is expected to have a life span that is shorter as compared to anon-mobile device. Further, the system may set the predetermined timeperiod, x, of Access Procedure 400 a to be different from thepredetermined time period, x, of Access Procedure 500 a. Again, thesystem sets x according to the expected life span of the saved accessdata. The saved access data of Access Procedure 400 a may have a longerexpected life span than that of the saved access data of AccessProcedure 500 a, for example because systems desire that MT data haveless latency. Thus, in embodiments, x of Access Procedure 400 a may beset at a moderately high value such as 1 hour, 12 hours, 18 hours, orthe like while x of Access Procedure 500 a may be set at seconds,minutes or the like. Thus, x is set to a value that balances latencyexpectations with the minimization of the number of times the AccessProcedure 400 a or 500 a is performed. In 608, the network has theoption of configuring the UE to ignore TA and/or MCS when sending datatransmissions. If desired, the network may configure the UE to ignore TAand/or MCS contingent on the type of data being transferred (e.g., TAmay be ignored when transmitting small data). The UE remains in thisconfiguration until the UE leaves the serving zone (608). Upon the UEleaving the serving zone, the system determines whether the UE left theserving network (609). If the UE remains in the serving network afterleaving the serving zone, the system configures the UE to perform toFIGS. 4 and 5 and sets x in light of the new serving zone's resourceallocations (607). If, in 609, the UE left the serving network andconnects to a new network (601), the system moves to 602. A UE may beconfigured and reconfigured multiple times as it moves from one zoneand/or network to another.

In an alternative embodiment to FIG. 6, a UE may be preconfigured,wherein the access information (e.g., SIB) is preconfigured and storedin the UE. When the UE is preconfigured with saved access data, theAccess Procedure 400 a and 500 a may be skipped because the LIE alreadyhas the access data stored therein. For example, the UE may bepreconfigured with SIB information that is compatible with the networkto which it is expected to communicate. An example UE is a thermostat,which is expected to be installed at a particular location (e.g.,address). Because the access data useful to communicate with the networkserving that UE at that particular location will be know prior toinstallation, the thermostat may be preconfigured with the known accessinformation (e.g. SIB). In such an embodiment, the thermostat may skipAccess Procedures 400 a and 400 b and simply send and receive data usingthe preconfigured access data and Data Transmission Procedures 400 b and500 b.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

The functional blocks and modules in FIGS. 3-6 may comprise processors,electronics devices, hardware devices, electronics components, logicalcircuits, memories, software codes, firmware codes, etc., or anycombination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the disclosure herein may be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure. Skilled artisans will also readilyrecognize that the order or combination of components, methods, orinteractions that are described herein are merely examples and that thecomponents, methods, or interactions of the various aspects of thepresent disclosure may be combined or performed in ways other than thoseillustrated and described herein.

The various illustrative logical blocks, modules, and circuits describedin connection with the disclosure herein may be implemented or performedwith a general-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with thedisclosure herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In one or more exemplary designs, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another.Computer-readable storage media may be any available media that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, such computer-readable media can compriseRAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other medium that canbe used to carry or store desired program code means in the form ofinstructions or data structures and that can be accessed by ageneral-purpose or special-purpose computer, or a general-purpose orspecial-purpose processor. Also, a connection may be properly termed acomputer-readable medium. For example, if the software is transmittedfrom a website, server, or other remote source using a coaxial cable,fiber optic cable, twisted pair, or digital subscriber line (DSL), thenthe coaxial cable, fiber optic cable, twisted pair, or DSL, are includedin the definition of medium. Disk and disc, as used herein, includescompact disc (CD), laser disc, optical disc, digital versatile disc(DVD), floppy disk and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media.

As used herein, including in the claims, the term “and/or,” when used ina list of two or more items, means that any one of the listed items canbe employed by itself, or any combination of two or more of the listeditems can be employed. For example, if a composition is described ascontaining components A, B, and/or C, the composition can contain Aalone; B alone; C alone; A and B in combination; A and C in combination;B and C in combination; or A, B, and C in combination. Also, as usedherein, including in the claims, “or” as used in a list of itemsprefaced by “at least one of” indicates a disjunctive list such that,for example, a list of “at least one of A, B, or C” means A or B or C orAB or AC or BC or ABC (i.e., A and B and C) or any of these in anycombination thereof.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein.

What is claimed is:
 1. A method for transmitting data comprising:transmitting a Chirp requesting user equipment (UE) access data based onat least a portion of synchronization information received from anetwork; in response to the Chirp, receiving and saving at least aportion of UE access data; utilizing at least a portion of the saved UEaccess data to send more than one discrete data transmission until apredetermined time period, associated with the saved UE access data,expires.
 2. The method of claim 1 comprising: ignoring a modulation andcarrier scheme (MCS) indicated in the synchronization information basedat least on a type of data being transmitted.
 3. The method of claim 1wherein when the Chirp is a small data transmission, an MCS indicated inthe synchronization information is ignored during the transmitting ofthe Chirp.
 4. The method of claim 1 wherein when the Chirp is not asmall data transmission, the transmitting the Chirp is based at least onan MCS of the synchronization information.
 5. The method of claim 1wherein at least one of: a carrier frequency of the Chirp, a modulationscheme of the Chirp, and a waveform of the Chirp is contingent onwhether the Chirp is a small data transmission.
 6. A user equipment (UE)for transmitting data comprising: a controller processor that sends toone or more antenna, via a transmit processor, a Chirp requesting UEaccess data based on at least a portion of synchronization informationreceived from a network; and a memory that saves at least a portion ofthe UE access data received in response to the Chirp, wherein theprocessor further utilizes at least a portion of the saved UE accessdata to send more than one discrete data transmission until apredetermined time period, associated with the saved UE access data,expires.
 7. The UE of claim 6 wherein the processor further ignores amodulation and carrier scheme (MCS) indicated in the synchronizationinformation based at least on a type of data being transmitted.
 8. TheUE of claim 6 wherein when the Chirp is a small data transmission, theprocessor ignores an MCS indicated in the synchronization informationwhile sending the Chirp.
 9. The UE of claim 6 wherein when the Chirp isnot a small data transmission, the processor sends the Chirp based atleast on an MCS of the synchronization information.
 10. The UE of claim6 wherein at least one of: a carrier frequency of the Chirp, amodulation scheme of the Chirp, and a waveform of the Chirp iscontingent on whether the Chirp is a small data transmission.
 11. Anon-transitory computer-readable medium having program code recordedthereon, the program code comprising: code for transmitting a Chirprequesting user equipment (UE) access data based on at least a portionof synchronization information received from a network; in response tothe Chirp, code for receiving and saving at least a portion of UE accessdata; code for utilizing at least a portion of the saved UE access datato send more than one discrete data transmission until a predeterminedtime period, associated with the saved UE access data, expires.
 12. Thenon-transitory computer-readable medium of claim 11 wherein the programcode further comprises: code for ignoring a modulation and carrierscheme (MCS) indicated in the synchronization information based at leaston a type of data being transmitted.
 13. The non-transitorycomputer-readable medium of claim 11 wherein when the Chirp is a smalldata transmission, an MCS indicated in the synchronization informationis ignored during the transmitting of the Chirp.
 14. The non-transitorycomputer-readable medium of claim 11 wherein when the Chirp is not asmall data transmission, the transmitting the Chirp is based at least onan MCS of the synchronization information.
 15. The non-transitorycomputer-readable medium of claim 11 wherein a carrier frequency of theChirp is contingent on whether the Chirp is a small data transmission.16. The non-transitory computer-readable medium of claim 11, wherein amodulation scheme of the Chirp is contingent on whether the Chirp is asmall data transmission.
 17. The non-transitory computer-readable mediumof claim 11, wherein a waveform of the Chirp is contingent on whetherthe Chirp is a small data transmission.
 18. A user equipment (UE) fortransmitting data comprising: a memory that saves preconfigured UEaccess data; and a processor that utilizes at least a portion of thepreconfigured UE access data to send more than one discrete datatransmission.
 19. The UE of claim 18 wherein the processor receives anddecodes a downlink transmission based at least on the preconfigured UEaccess data.
 20. The UE of claim 19 wherein prior to receiving thedownlink transmission, the processor receives a keep alive transmissionthat notifies the UE about the downlink transmission.
 21. The UE ofclaim 18 wherein the processor receives synchronization information froma network and transmits at least one of the discrete data transmissionsbased at least on a portion of the synchronization information and aportion of the preconfigured UE access data.
 22. The UE of claim 21wherein the processor further ignores a modulation and carrier scheme(MCS) indicated in the synchronization information based at least on atype of data being transmitted in the at least one of the discrete datatransmissions.
 23. The UE of claim 21 wherein the at least one of thediscrete data transmissions is a Chirp, and wherein when the Chirp is asmall data transmission, the processor ignores an MCS indicated in thesynchronization information while sending the Chirp.
 24. The UE of claim21 wherein when the at least one of the discrete data transmissions isnot a small data transmission, the processor sends the at least one ofthe discrete data transmissions based at least on an MCS of thesynchronization information.
 25. The UE of claim 21 wherein the at leastone of the discrete data transmissions is a Chirp, and wherein at leastone of a carrier frequency of the Chirp, a modulation scheme of theChirp, and a waveform of the Chirp is contingent on whether the Chirp isa small data transmission.